Collaborative Document Editing

ABSTRACT

Various features and processes related to document collaboration are disclosed. In some implementations, animations are presented when updating a local document display to reflect changes made to the document at a remote device. In some implementations, a user can selectively highlight changes made by collaborators in a document. In some implementations, a user can select an identifier associated with another user to display a portion of a document that includes the other user&#39;s cursor location. In some implementations, text in document chat sessions can be automatically converted into hyperlinks which, when selected, cause a document editor to perform an operation.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.17/135,530, filed Dec. 18, 2020, which is a continuation of U.S. patentapplication Ser. No. 15/999,716, filed Aug. 20, 2018, now U.S. Pat. No.10,880,098, which is a continuation of U.S. patent application Ser. No.15/068,490, filed Mar. 11, 2016, now U.S. Pat. No. 10,055,394, which isa continuation of U.S. patent application Ser. No. 13/332,323, filedDec. 20, 2011, now abandoned, the disclosures of which are incorporatedherein by reference as if fully disclosed herein.

TECHNICAL FIELD

The disclosure generally relates to document editing and collaboration.

BACKGROUND

Multi-user collaboration on documents is often necessary in industry,academics and other endeavors. For example, software developers may needto collaborate while writing a software architecture document. Studentsmay need to collaborate on a presentation or academic paper.Collaboration on a document is often accomplished by editing thedocument sequentially (e.g., one collaborator can edit the document at atime). Alternatively, collaboration on a document can be accomplished byhaving each collaborator edit a different version of the document andthen merging the documents together. These methods of collaborating on adocument can often be cumbersome, time consuming and inefficient.

SUMMARY

Various features and processes related to document collaboration aredisclosed. In some implementations, animations are presented whenupdating a local document display to reflect changes made to thedocument at a remote device. In some implementations, a user canselectively highlight changes made by collaborators in a document. Insome implementations, a user can select an identifier associated withanother user to display a portion of a document that includes the otheruser's cursor location. In some implementations, text in document chatsessions can be automatically converted into hyperlinks which, whenselected, cause a document editor to perform an operation.

Particular implementations provide at least the following advantages:Animating changes to a document can quickly draw a user's attention tothe changes and provide a more entertaining collaboration experience.Selectively highlighting document changes can allow a user to quicklyfind important changes to the document. Jumping to another user's cursorlocation allows users' to quickly view the changes that other users arecurrently making to a document. Document chat links allow collaboratingusers to communicate and help each other in a more efficient manner.

Details of one or more implementations are set forth in the accompanyingdrawings and the description below. Other features, aspects, andpotential advantages will be apparent from the description and drawings,and from the claims.

DESCRIPTION OF DRAWINGS

FIG. 1 illustrates an example system for concurrent documentcollaboration.

FIG. 2 illustrates an example graphical user interface for presentingcollaboration effects.

FIG. 3 illustrates an example graphical interface for presenting textchanges made to a document.

FIG. 4 illustrates an example graphical interface for selective changehighlighting.

FIG. 5 illustrates an example graphical interface for accepting orrejecting changes to a document.

FIG. 6 illustrates an example graphical interface for jumping to acollaborator's cursor location.

FIG. 7 illustrates an example graphical interface for presenting smarttext in a document chat session.

FIG. 8 is a flow diagram of an example process for presentingcollaboration effects.

FIG. 9 is a flow diagram of an example process for selective changehighlighting.

FIG. 10 is flow diagram of an example process for permissions baseddocument change tracking.

FIG. 11 is a flow diagram of an example process for jumping to acollaborator's cursor location.

FIG. 12 is a flow diagram of an example process for smart text indocument chat.

FIG. 13 is a block diagram of an example computing device forimplementing the features and processes of FIGS. 1-12 .

Like reference symbols in the various drawings indicate like elements.

DETAILED DESCRIPTION Document Collaboration

FIG. 1 illustrates an example system 100 for concurrent documentcollaboration. In some implementations, two or more users cancollaborate on a document simultaneously. For example, document 102 canbe a word processing document, a spreadsheet document, a multi-mediadocument, or any other document that can be edited. In someimplementations, document 102 can be stored on a computing device withinnetwork 104. Network 104 can be a network that includes wired orwirelessly connected computing devices. For example, network 104 caninclude the Internet (e.g., World Wide Web), an intranet, or a homenetwork. In some implementations, network 104 can be coupled to orinclude computing devices 106, 108 and/or 110. For example, computingdevices 106, 108 and 110 can include any computing device, such as alaptop computer, desktop computer, tablet computer, smartphone, etc.

In some implementations, users of computing devices 106, 108 and 110 cancollaborate on editing document 102. In some implementations, computingdevices 106, 108 and 110 can provide access to document 102 such thatusers can make changes or edit document 102 concurrently. For example,computing devices 106, 108 and 110 can provide a view 102A, 102B, 102Cof document 102. Document views 102A, 102B and 102C can be a local copyof document 102 that is automatically synchronized with document 102 innetwork 104. Document views 102A, 102B and 102C can be representationsof the actual document 102 such that changes made within the documentviews are made near real-time to document 102. In some implementations,changes made to documents view 102A on computing device 106 can besynchronized with document 102 on network 104 and viewed within documentviews 102B and 102C on computing devices 108 and 110 as the changes arebeing made within document view 102A. For example, as a character, word,object or other content is added to document 102 through document view102A, the added content can be synchronized to and viewed withindocument views 102B and 102C. Thus, the changes within document view102A can be synchronized with document 102 and seen within documentviews 102B and 102C in approximately real-time.

Collaboration Effects

FIG. 2 illustrates an example graphical interface 250 for presentingcollaboration effects. In some implementations, graphical interfaces 200and 250 can correspond to an interface for viewing or editing documentview 102A, 102B or 102C. In some implementations, an animation can beused for presenting changes made to a document. For example, when a usermakes changes to a document within document view 102A on computingdevice 106, the changes can be presented to a user of computing device108 within document view 102B along with an animation associated withthe change.

In some implementations, when an object within a document is moved on afirst device, the move can be animated on a second device. For example,interface 200 can display document view 102A on computing device 106.Document view 102A can display an object 202A corresponding to an objectwithin document 102. A user of computing device 106 can move object 202Ato a new location within document view 102A. The new location of object202A can be synchronized with document 102 and displayed in documentview 102C (interface 250) of computing device 110. For example, thelocation of corresponding object 202B in document view 102C can change.In some implementations, the change of location of object 202B indocument view 102C can be animated. For example, object 202B in documentview 102C can be animated to move from the object's original location tothe object's new location as specified by the user of computing device106. In some implementations, the move animation can include resizingobject 202B. For example, object 202B can be scaled up or scaled down insize during the move animation, as illustrated by FIG. 2 .

In some implementations, when an object is added to, removed from, orresized on a document on a first device, the addition, removal orresizing of the object can be animated on a second device. For example,object 204A can be added to document view 102A (interface 200). Theaddition of object 204A within document view 102A can be synchronized todocument 102 and can be displayed within document views 102B and 102C.For example, corresponding object 204B in can be added to document view102C (interface 250). In some implementations, the addition of object204B to document view 102C can be animated. For example, object 204B canbe animated to expand out (e.g., grow) from a single point until object204B is the size of the added object 204A. In some implementations,object 204B can be animated to bounce into view on document view 102C.In some implementations, a deletion of an object can be presented withan animation. For example, if object 204A is deleted within documentview 102A, object 204B can be shrunk (e.g., scaled down) to a singlepoint and removed from document view 102C. Similarly, if object 204A isresized, object 204B can be animated to shrink or grow correspondingly.

In some implementations, if a user changes an attribute of an object ona first device, the change can be presented along with an animation on asecond device. For example, if a user changes the color of object 206A(e.g., from orange to blue), object 206B can be modified to reflect thecolor change (e.g., object 206B will turn blue). In someimplementations, an animation will be presented while changing colors.For example, a transition animation (e.g., a shaking, rotation,oscillation animation) can be presented when object 206B is changed fromorange to blue.

In some implementations, other document change animations can bepresented. For example, when a user on a first device edits a worksheetcell of a spreadsheet application, a highlight animation can bedisplayed on a second device as the changes to the worksheet cell aredisplayed on the second device. For example, the worksheet celldisplayed on the second device can temporarily fill with color (e.g.,yellow) when the worksheet cell is edited on the first device to drawthe user's attention to the edited cell.

The document change animations described above can serve not only topresent an interesting collaborative environment for document editingbut can also serve to draw a user's attention to edits that arecurrently being made to the document by other users (collaborators).

Tracking Changes in Real-Time

FIG. 3 illustrates an example graphical interface 300 for presentingtext changes made to a document. In some implementations, graphicalinterface 300 can correspond to an interface for viewing or editingdocument view 102A, 102B or 102C. For example, changes made to document102 by a user of computing device 106 through document view 102A can beviewed by a user of computing device 108 in document view 102B. In someimplementations, the changes made to document 102 can be tracked,associated with a user who made the changes and highlighted so thatother users (collaborators) can view the changes.

In some implementations, changes to document 102 (e.g., through documentviews 102A, 102B and/or 102C) can be tracked. For example, a documenteditor software application can have a track changes feature. In someimplementations, if the track changes feature is turned on, changes madeto the document will be provisional pending acceptance of the changesinto the document. In some implementations, provisional changes can bemarked up or annotated. For example, text added to a document can beunderlined. Text deleted from a document can be presented with a linethrough the text (e.g., strikethrough formatted), for example.

In some implementations, the provisional changes can be associated withmetadata that identifies who (e.g., which user) made the changes. Forexample, if a user named Bob made changes 302, then the metadataassociated with change 302 will include information that identifies Bobas the user who made change 302. If a user named Fred made changes 304,then the metadata associated with change 304 will include informationthat identifies Fred as the user who made change 304.

In some implementations, the provisional changes can be highlighted. Forexample, the provisional changes can be color highlighted according towho made the provisional changes. Bob, for example, can be associatedwith the color yellow and provisional changes made by Bob can behighlighted in yellow (e.g., have a yellow background). Likewise, Fredcan be associated with the color green and provisional changes made byFred can be highlighted in green, for example.

In some implementations, the provisional changes, including formatting,markup, annotating and/or highlighting, can be seen by collaborators(users) as the provisional changes are made. For example, while a userof computing device 106 is making provisional changes to document 102through document view 102A, users of computing devices 108 and 110 canview the provisional changes through respective document views 102B and102C. As each character, word, sentence or object is added, deleted ormodified in document view 102A, the provisional changes can be displayedin document views 102B and 102C along with the appropriate markup,formatting, annotations and/or highlighting, as described above.

Selective Change Highlighting

FIG. 4 illustrates an example graphical interface 400 for selectivechange highlighting. In some implementations, graphical interface 400can correspond to an interface for viewing or editing document view102A, 102B or 102C. In some implementations, a user can select whichprovisional changes will be highlighted. For example, graphicalinterface 400 can include graphical element 402. Graphical element 402can present information about the number of collaborators (e.g., users,editors) that are currently accessing the document. For example, if fourusers are currently viewing, editing or otherwise accessing the document(e.g., document 102), graphical element 402 will display informationthat indicates that four users are accessing the document.

In some implementations, graphical element 402 is selectable. Forexample, a user can select graphical element 402 to cause graphicalelement 404 to display. For example, graphical element 404 can be apopup menu, a pull-down menu, or a dialog window. In someimplementations, graphical element 404 can display information about theusers who are currently accessing the document and/or users who haveaccessed the document in the past. For example, graphical element 404can present a list (e.g., a collaborator list) of the names of theusers, each user's online status and/or the highlighting colorassociated with each user. In some implementations, graphical element404 can provide access to additional features of graphical interface400. For example, a user can select the “Highlight Changes” feature ofgraphical interface 400 to display graphical element 406.

In some implementations, graphical element 406 can present selectablechange highlighting options. For example, a user can select an option tohave graphical interface 400 highlight only the changes made by the userso that the user can quickly find the user's own provisional changes inthe document. A user can select an option to highlight only the changesmade by others. For example, the user may be interested in quicklyfinding and viewing the provisional changes made by other collaborators.A user can select an option to remove all change highlighting from thedocument. A user can select an option to highlight all changes in thedocument. For example, a user can deselect a currently selected optionsuch that none of the change highlighting options are selected to causeall provisional changes to be highlighted in the document.

In some implementations, selective change highlighting can be performedon non-provisional changes as well as provisional changes. For example,portions of text within a document can be associated with the user whoadded the text to the document regardless of whether the added text isprovisional or non-provisional. A user can select one of the changehighlighting options presented on graphical element 406 to have the textassociated with the selected highlighting option (e.g., text associatedwith the user, text associated with other users, all text highlighted byuser, or no text highlighting) highlighted. For example, if the userselects the option for highlighting all text, then all of the textwithin the document will be highlighted according to the colorsassociated with the users who added the respective portions text.

Track Changes Permissions

FIG. 5 illustrates an example graphical interface 500 for accepting orrejecting changes to a document. In some implementations, provisionalchanges to a document can be accepted into or rejected from thedocument. For example, when provisional changes are accepted into thedocument the provisional changes become non-provisional changes (e.g.,permanent changes subject to later edits) to the document. In someimplementations, provisional changes can be accepted into the documentby selecting a provisional change (e.g., placing the cursor over orhighlighting the text associated with the provisional change) andselecting graphical element 502 (e.g., accept button). Provisionalchanges can be rejected from the document by selecting a provisionalchange and selecting graphical element 504 (e.g., reject button). Insome implementations, provisional changes can be accepted or rejectedthrough graphical element 506. For example, graphical element 506 can bedisplayed in response to a user selecting graphical element 508.

In some implementations, graphical element 506 can display changetracking options. For example, graphical element 506 can displayselectable options to accept all changes, reject all changes, acceptselected changes (similar to graphical element 502), reject selectedchanges (similar to graphical element 504) and an option to turn offchange tracking. A user can select any of the options to cause thecorresponding action to be performed. For example, if a user selects the‘accept all changes’ option, all of the provisional changes to thedocument will be accepted into the document as non-provisional changesto the document. Likewise, if the user selects the ‘reject all changes’option, all of the provisional changes will be rejected (e.g., removed)from the document.

In some implementations, only an authorized user of the document canaccept provisional changes into the document. In some implementations,the document can be associated with track changes permissions. The trackchanges permissions can be document metadata that identifies which userscan perform track changes operations. For example, the track changespermissions can identify which users can turn track changes on and offand which users can accept or reject changes to the document. When thetrack changes feature is turned on, any user can make provisionalchanges to the document. However, only an authorized user can accept andreject provisional changes or turn on or off the track changes feature.In some implementations, a user can be authorized to perform specifictrack changes operations. For example, permissions can be defined thatallow a user to turn on the track changes feature but prevent the sameuser from turning off the track changes feature.

In some implementations, an authorized user can perform track changesoperations (e.g., accepting changes, rejecting changes, turning on oroff track changes) as other users are editing the document. For example,the authorized user can view provisional changes as the changes arebeing made to the document by users and accept the provisional changeswhen they appear.

In some implementations, only the owner of a document will be authorized(e.g., will have permissions) to perform track changes operations. Forexample, the document owner can be a project supervisor who has assignedvarious editing tasks to other users. The other users can edit thedocument as they perform their tasks, the edits can be synchronized innear real-time to the document and the other users, the edits can betracked if track changes is turned on, and the tracked changes can bepresented as provisional changes to the document along with theappropriate markups, highlighting, formatting and annotations, asdescribed above. The document owner can accept and reject provisionalchanges to the document and turn on or off the track changes feature.

In some implementations, an unauthorized user (e.g., non-owner user)will be unable to accept or reject changes to a document or turn on oroff the track changes feature. For example, graphical interface 500 canprevent the non-owner user from selecting graphical elements 502 and 504and prevent the non-owner user from displaying graphical element 506 orselecting any of the options on graphical element 506. Graphicalelements 502, 504, 506 and/or 508 can be disabled (e.g., not selectable)on graphical interface 500, for example.

Jump to Collaborator's Cursor

FIG. 6 illustrates an example graphical interface 600 for jumping to acollaborator's cursor location. In some implementations, a user cancause another user's cursor location to be displayed on graphicalinterface 600. For example, a user can select another user's name (e.g.,George) displayed on graphical element 404. In response to theselection, the portion of the document that includes the selected user's(e.g., George's) current cursor location will be displayed. Thus, a usercan quickly go to and view the location in the document where the otheruser is making edits.

Smart Text in Document Chat

FIG. 7 illustrates an example graphical interface 700 for presentingsmart text in a document chat session. In some implementations, adocument editor can include a chat feature. For example, collaborators(users) who are working on a document can send messages to each otherthrough a chat feature of the document editor. In some implementations,a user can open chat window 702 by selecting graphical element 704(e.g., chat button) or the ‘chat window’ option of graphical element404. For example, a user can select a user from the list of usersdisplayed on graphical element 404 and then select the ‘chat window’option to initiate a chat session with the selected user. If a user hasreceived a chat message, graphical element 704 can display an indicationof the number of chat messages received. The user can select graphicalelement 704 to view the received chat messages. In some implementations,chat window 702 can display automatically when a new chat message isreceived.

In some implementations, chat window area 706 can display received chatmessages. In some implementations, chat window area 708 can be an inputarea for composing messages to send to other users. For example, a usercan use a keyboard (e.g., virtual or physical) to type text into area708 and press the ‘enter’ or ‘return’ key on the keyboard to cause thetext message to be sent to another user.

In some implementations, chat messages can include text that relates tofunctions of the document editor and/or attributes of the document. Forexample, text received in a chat message can refer to a page number,paragraph, a chapter, or a section of a document. The text can refer toa figure, graph or other media item embedded in the document. The chatmessage text can refer to an operation, menu item or feature of thedocument editor. For example, a user can assist another user byidentifying a particular editing menu in a chat session.

In some implementations, text references to document attributes and/ordocument editor features can be converted into selectable links (e.g.,hyperlinks) that, when selected, cause some document editor function tobe performed. For example, a textual page reference (e.g., ‘page 5’) canbe converted into a link, which when selected, causes the documenteditor to display page five (5) of the document. The link causes a ‘goto page’ function to be performed by the document editor. A textualreference to a ‘drawing tool’ of the document editor can be converted toa link which, when selected, can cause a corresponding drawing tool tobe displayed in the document editor. In some implementations, the linkcan be displayed with special formatting (e.g., underlining) orhighlighting to let the user know that the text of the link isselectable, as illustrated by FIG. 7 .

Example Processes

FIG. 8 is a flow diagram of an example process 800 for presentingcollaboration effects. In some implementations, when a document changemade on a first device is displayed on a second device, an animationassociated with the change is displayed.

At step 802, a document is displayed on a first device. For example, adocument can be displayed and edited by multiple different users onmultiple different devices.

At step 804, change information is received from a second device. Forexample, a user on one device can make edits (changes) to the document.Information describing the changes can be transmitted to the otherdevices that are displaying the document. The change information caninclude information that identifies objects that were changed in thedocument (e.g., media objects, text, etc.), the type of changes made(e.g., additions, deletions, moves, formatting, etc.) and locationswhere the changes were made to the document.

At step 806, the changes to be made to the document are determined. Forexample, once the change information is received, changes to the localdocument can be determined based on the change information. For example,the object information, the change type information and the locationinformation can be analyzed to determine what changes need to be made tothe document. The change information can specify that an image objectwas added to the document on page ten (10), for example.

At step 808, an animation is displayed according to the type of documentchange. For example, the local document editor can be configured withanimation information. Animation information can specify what kind ofanimation to display for a particular document change. For example, theanimation information can include a mapping of animation type to objecttype and/or change type. For example, an addition change type can bemapped to a scale up (e.g., enlarge, grow) animation. A move change typecan be mapped to a move animation. A change to an image object can bemapped to a shake (e.g., wiggle) animation.

In some implementations, an animation can be determined based on thechange information. For example, the object type and/or the change typein the change information can be used to lookup the appropriateanimation. Once the animation is determined, the animation can bedisplayed at the document location specified in the change information.For example, the object to be added, deleted, modified or moved can beanimated according to the change information and the animationinformation.

At step 810, the changes can be applied to the document. For example,after or while the animation is displayed, the changes identified in thechange information can be applied to the document. For example, theobject can be added, deleted, modified, or moved within the documentaccording to the change information.

FIG. 9 is a flow diagram of an example process 900 for selective changehighlighting. In some implementations, a user can select whichcollaborators' changes to highlight.

At step 902, a document is displayed on a first device. For example,multiple users can collaborate on a document from multiple devices.

At step 904, change information is received from a second device. Forexample, each user can make changes to the document. Each user's changescan be transmitted to the other user's devices. Thus, a user's devicecan receive change information from one or more other users' devices.For example, the change information can include a description of thetype of change, such as an identification and location of text that hasbeen added or deleted from the document and an identification of a usercorresponding to each change.

At step 906, changes are made to the document according to the changeinformation. For example, each user's changes can be incorporated intothe document displayed on the other users' devices. If track changes isturned on, each users' changes will be displayed as provisional changes(e.g., marked up and/or highlighted) until the provisional changes areaccepted into the document.

At step 908, input selecting one or more collaborators is received. Forexample, a user can select to highlight the user's own changes, otherusers' changes, all changes or no changes.

At step 910, the selected collaborators' changes are highlighted. Oncethe user has selected whose changes to highlight, the document displaycan be modified to highlight the selected users' changes. For example,change highlighting can be performed by changing the background color oftext from white to a color, such as green, yellow or red. In someimplementations, only the selected users' changes will be highlighted.

FIG. 10 is flow diagram of an example process 1000 for permissions baseddocument change tracking. In some implementations, provisional changesto a document can only be accepted by authorized users. In someimplementations, an authorized user is an owner of the document. In someimplementations, an authorized user is determined based on permissionsassociated with the document.

At step 1002, a document is requested from a document server. Forexample, a user device can request a document from the server. Therequest can include identification information for the user. Thedocument can be associated with multiple users and multiple devices. Theusers can collaborate on the document and make changes or edits to thedocument concurrently, for example.

At step 1004, document information is received from the server alongwith document permissions information. For example, the documentinformation can include content and formatting information for thedocument that defines how the document content should be displayed. Thedocument permissions information can indicate whether the requestinguser has permission to accept or reject provisional changes to thedocument. For example, when the server receives the document request,the server can determine whether the requesting user has permissions toaccept or reject changes to the document and whether the requesting usercan turn on and off the track changes feature. The server can look upthe user's permissions based on the user identification informationincluded in the document request.

At step 1006, the user is prevented from accessing the track changesoptions. For example, if the document permissions information indicatesthat the requesting user is not authorized to accept or rejectprovisional changes to the document and/or is not authorized to turn onor off the track changes feature, the user will be prevented frominvoking any of these track changes options. For example, the graphicalinterface elements for accepting and rejecting changes and turning onand off the track changes features can be disabled so that the usercannot select these elements.

FIG. 11 is a flow diagram of an example process for jumping to acollaborator's cursor location. At step 1102, a document can bedisplayed to a user on a first device. For example, multiple users onmultiple devices can collaborate on editing a document.

At step 1104, the first device can receive information describinganother user's cursor location in the document. For example, each user'sdevice can communicate information to other devices. For example, auser's device can communicate to other users' devices informationdescribing changes made to the document and current cursor locationinformation. The information can be communicated directly from device todevice or can be transmitted to and forwarded from the server thatmanages (stores) the document.

At step 1106, input selecting the other user can be received. Forexample, graphical interface 600 can display a list of user's who arecurrently accessing the document and a user can select one of the usersin the list, as described above with reference to FIG. 6 .

At step 1108, the selected user's cursor location can be displayed. Forexample, a portion of the document that includes the location of theselected user's cursor can be displayed. If the user's cursor is locatedon page six, then page six can be displayed, for example.

FIG. 12 is a flow diagram of an example process 1200 for smart text indocument chat. At step 1202, a document is presented in a graphicalinterface of a device. For example, the document can be presented in auser interface of a document editing application.

At step 1204, a text message is received. For example, the documentediting application can include a chat feature that allows user tocommunicate while collaborating on the document and a user can receive atext chat message while viewing the document.

At step 1206, the text of the chat message is analyzed for keywords. Forexample, the document editing application and/or the chat feature can beconfigured to recognize keywords related to document attributes and/ordocument editing application features and functions. Document attributekeywords can include ‘page,’ chapter,′ and ‘figure,’ among others.Document editing application keywords can include ‘insert,’ ‘open,’ and‘format,’ among others. Each of these keywords can correspond to adocument editor function. For example, the keyword ‘page’ can correspondto a ‘go to page’ function. The keyword ‘insert’ can correspond to aninsert menu item.

At step 1208, the words matching configured keywords are converted intohyperlinks. For example, when a chat message is received containing thetext “See page 5,” the word ‘page’ will recognized as a keyword and theword and the page number ‘5’ will be converted into a hyperlink. Thehyperlink will be configured to invoke an operation corresponding to therecognized keyword. For example, the hyperlink can invoke a ‘go to page’function, invoke a menu item, or invoke a tool of the document editor.

At step 1210, the text message and the hyperlink will be displayed. Forexample, the chat message text will be displayed in a chat window. Theportion of the chat message text that includes ‘page 5’ will bedisplayed as a hyperlink. At step 1212, a selection of the hyperlink isreceived. For example, a user can select the ‘page 5’ hyperlink in thechat window.

At step 1214, the document editing application can perform an operationbased on the hyperlink. For example, when the ‘page 5’ hyperlink isselected, the document editing application can display page 5 of thedocument. Other operations, such as invoking an editing tool or menuitem, can be invoked based on the configuration of the hyperlink.

Example Device Architecture

FIG. 13 is a block diagram 1300 of an example computing device (e.g.,computing device 106, 108 and/or 110 of FIG. 1 ) for implementing thefeatures and processes of FIGS. 1-12 . The device can include a memoryinterface 1302, one or more data processors, image processors and/orcentral processing units 1304, and a peripherals interface 1306. Thememory interface 1302, the one or more processors 1304 and/or theperipherals interface 1306 can be separate components or can beintegrated in one or more integrated circuits. The various components inthe device can be coupled by one or more communication buses or signallines.

Sensors, devices, and subsystems can be coupled to the peripheralsinterface 1306 to facilitate multiple functionalities. For example, amotion sensor 1310, a light sensor 1312, and a proximity sensor 1314 canbe coupled to the peripherals interface 1306 to facilitate orientation,lighting, and proximity functions. Other sensors 1316 can also beconnected to the peripherals interface 1306, such as a global navigationsatellite system (GNSS) (e.g., GPS receiver), a temperature sensor, abiometric sensor, or other sensing device, to facilitate relatedfunctionalities.

A camera subsystem 1320 and an optical sensor 1322, e.g., a chargedcoupled device (CCD) or a complementary metal-oxide semiconductor (CMOS)optical sensor, can be utilized to facilitate camera functions, such asrecording photographs and video clips. The camera subsystem 1320 and theoptical sensor 1322 can be used to collect images of a user to be usedduring authentication of a user, e.g., by performing facial recognitionanalysis.

Communication functions can be facilitated through one or more wirelesscommunication subsystems 1324, which can include radio frequencyreceivers and transmitters and/or optical (e.g., infrared) receivers andtransmitters. The specific design and implementation of thecommunication subsystem 1324 can depend on the communication network(s)over which the device is intended to operate. For example, the devicecan include communication subsystems 1324 designed to operate over a GSMnetwork, a GPRS network, an EDGE network, a Wi-Fi or WiMax network, anda Bluetooth™ network. In particular, the wireless communicationsubsystems 1324 can include hosting protocols such that the device canbe configured as a base station for other wireless devices.

An audio subsystem 1326 can be coupled to a speaker 1328 and amicrophone 1330 to facilitate voice-enabled functions, such as speakerrecognition, voice replication, digital recording, and telephonyfunctions.

The I/O subsystem 1340 can include a touch-surface controller 1342and/or other input controller(s) 1344. The touch-surface controller 1342can be coupled to a touch surface 1346. The touch surface 1346 andtouch-surface controller 1342 can, for example, detect contact andmovement or break thereof using any of a plurality of touch sensitivitytechnologies, including but not limited to capacitive, resistive,infrared, and surface acoustic wave technologies, as well as otherproximity sensor arrays or other elements for determining one or morepoints of contact with the touch surface 1346.

The other input controller(s) 1344 can be coupled to other input/controldevices 1348, such as one or more buttons, rocker switches, thumb-wheel,infrared port, USB port, and/or a pointer device such as a stylus. Theone or more buttons (not shown) can include an up/down button for volumecontrol of the speaker 1328 and/or the microphone 1330.

In one implementation, a pressing of the button for a first duration candisengage a lock of the touch surface 1346; and a pressing of the buttonfor a second duration that is longer than the first duration can turnpower to the device on or off. Pressing the button for a third durationcan activate a voice control, or voice command, module that enables theuser to speak commands into the microphone 1330 to cause the device toexecute the spoken command. The user can customize a functionality ofone or more of the buttons. The touch surface 1346 can, for example,also be used to implement virtual or soft buttons and/or a keyboard.

In some implementations, the device can present recorded audio and/orvideo files, such as MP3, AAC, and MPEG files. In some implementations,the mobile device 100 can include the functionality of an MP3 player,such as an iPod™. The device can, therefore, include a 36-pin connectorthat is compatible with the iPod. Other input/output and control devicescan also be used.

The memory interface 1302 can be coupled to memory 1350. The memory 1350can include high-speed random access memory and/or non-volatile memory,such as one or more magnetic disk storage devices, one or more opticalstorage devices, and/or flash memory (e.g., NAND, NOR). The memory 1350can store an operating system 1352, such as Darwin, RTXC, LINUX, UNIX,OS X, WINDOWS, or an embedded operating system such as VxWorks.

The operating system 1352 can include instructions for handling basicsystem services and for performing hardware dependent tasks. In someimplementations, the operating system 1352 can be a kernel (e.g., UNIXkernel). In some implementations, the operating system 1352 can includeinstructions for performing voice authentication. For example, operatingsystem 1352 can implement the document collaboration features describedwith reference to FIGS. 1-12 .

The memory 1350 can also store communication instructions 1354 tofacilitate communicating with one or more additional devices, one ormore computers and/or one or more servers. The memory 1350 can includegraphical user interface instructions 1356 to facilitate graphic userinterface processing; sensor processing instructions 1358 to facilitatesensor-related processing and functions; phone instructions 1360 tofacilitate phone-related processes and functions; electronic messaginginstructions 1362 to facilitate electronic-messaging related processesand functions; web browsing instructions 1364 to facilitate webbrowsing-related processes and functions; media processing instructions1366 to facilitate media processing-related processes and functions;GNSS/Navigation instructions 1368 to facilitate GNSS andnavigation-related processes and instructions; and/or camerainstructions 1370 to facilitate camera-related processes and functions.

The memory 1350 can store other software instructions 1372 to facilitateother processes and functions, such as the document collaborationprocesses and functions described with reference to FIGS. 1-12 . Forexample, the software instructions can include instructions forperforming voice authentication on a per application or per featurebasis and for allowing a user to configure authentication requirementsof each application or feature available on device 100.

The memory 1350 can also store other software instructions (not shown),such as web video instructions to facilitate web video-related processesand functions; and/or web shopping instructions to facilitate webshopping-related processes and functions. In some implementations, themedia processing instructions 1366 are divided into audio processinginstructions and video processing instructions to facilitate audioprocessing-related processes and functions and video processing-relatedprocesses and functions, respectively. An activation record andInternational Mobile Equipment Identity (IMEI) 1374 or similar hardwareidentifier can also be stored in memory 1350.

Each of the above identified instructions and applications cancorrespond to a set of instructions for performing one or more functionsdescribed above. These instructions need not be implemented as separatesoftware programs, procedures, or modules. The memory 1350 can includeadditional instructions or fewer instructions. Furthermore, variousfunctions of the device can be implemented in hardware and/or insoftware, including in one or more signal processing and/or applicationspecific integrated circuits.

What is claimed is:
 1. A method comprising: presenting, on a display of a first device, a first portion of a document in a graphical user interface of a document editing application; receiving, at the first device and from a second device, a text message including one or more words; after receiving the text message, identifying that a set of one or more words of the one or more words is associated with a location within the document; based on identifying that the set of one or more words is associated with the location, presenting, as a replacement for the set of one or more words, a selectable link; and in response to selection of the selectable link, causing the document editing application to display, in the graphical user interface, a second portion of the document that is different from the first portion of the document, wherein the second portion corresponds to the location.
 2. The method of claim 1, wherein: the document editing application includes a chat interface; and the text message is displayed in the chat interface.
 3. The method of claim 2, wherein the chat interface and a portion of the document are simultaneously displayed in the graphical user interface of the document editing application.
 4. The method of claim 1, wherein the set of one or more words comprises a page number of the document.
 5. The method of claim 1, wherein the set of one or more words comprises a reference to a figure contained in the document.
 6. The method of claim 1, further comprising displaying a cursor location associated with the second device on the graphical user interface associated with the first device.
 7. The method of claim 1, wherein: the document editing application receiving a modification to the document from the second device at a second location; and the document editing application changes a presentation of the document on the display of the first device to reflect the modification to the document. 